docs: Add UCAI (abi-to-mcp) to registry#3221
Closed
nirholas wants to merge 1 commit intomodelcontextprotocol:mainfrom
Closed
docs: Add UCAI (abi-to-mcp) to registry#3221nirholas wants to merge 1 commit intomodelcontextprotocol:mainfrom
nirholas wants to merge 1 commit intomodelcontextprotocol:mainfrom
Conversation
<!-- Provide a brief summary of your changes --> Add UCAI (abi-to-mcp) - Smart Contract to MCP Server Generator ## Motivation and Context Added UCAI to the MCP registry. UCAI is a tool that converts Ethereum smart contract ABIs into fully functional MCP servers, enabling AI assistants like Claude to interact with any smart contract on any EVM-compatible chain. Key features: - **CLI & Python API**: `pip install abi-to-mcp` - generate MCP servers from contract addresses or ABI files - **Web Builder**: [mcp.ucai.tech](https://mcp.ucai.tech) - no-install browser-based server generation - **Security Scanner**: AI-powered contract risk analysis with 50+ security patterns - **Contract Whisperer**: Plain English explanations of smart contract functionality - **Multi-chain Support**: Ethereum, Base, Arbitrum, Polygon, Optimism, BSC, and more - **Safety First**: Write operations simulate by default, read-only mode available This enables AI agents to query token balances, inspect NFT metadata, simulate transactions, and execute DeFi operations through natural language. Documentation: https://docs.ucai.tech GitHub: https://github.com/nirholas/UCAI PyPI: https://pypi.org/project/abi-to-mcp/ Web App: https://mcp.ucai.tech ## How Has This Been Tested? <!-- Have you tested this in a real application? Which scenarios were tested? --> - Generated MCP servers for ERC-20 tokens (USDC, USDT) - Tested with Uniswap, Aave, and NFT collections (BAYC) - Integrated with Claude Desktop successfully - Utilized by numerous FinTech enterprise projects - 876 unit tests with 98% coverage ## Breaking Changes <!-- Will users need to update their code or configurations? --> None - this is a new addition to the registry. ## Types of changes <!-- What types of changes does your code introduce? Put an `x` in all the boxes that apply: --> - [ ] Bug fix (non-breaking change which fixes an issue) - [x] New feature (non-breaking change which adds functionality) - [ ] Breaking change (fix or feature that would cause existing functionality to change) - [ ] Documentation update ## Checklist <!-- Go over all the following points, and put an `x` in all the boxes that apply. --> - [x] I have read the [MCP Documentation](https://modelcontextprotocol.io) - [x] My code follows the repository's style guidelines - [x] New and existing tests pass locally - [x] I have added appropriate error handling - [x] I have added or updated documentation as needed ## Additional context <!-- Add any other context, implementation notes, or design decisions --> UCAI follows the Model Context Protocol specification and generates servers using the official MCP Python SDK. All generated servers include: - Type-safe tool definitions mapped from Solidity types - Transaction simulation for write operations - Event queries as MCP resources - Proper error handling and gas estimation
Member
|
Since #3046, new entries are no longer added to the README's third-party server list. Going forward, please consider registering it in the MCP Registry. Thank you. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Add UCAI (abi-to-mcp) - Smart Contract to MCP Server Generator
Motivation and Context
Added UCAI to the MCP registry. UCAI is a tool that converts Ethereum smart contract ABIs into fully functional MCP servers, enabling AI assistants like Claude to interact with any smart contract on any EVM-compatible chain.
Key features:
pip install abi-to-mcp- generate MCP servers from contract addresses or ABI filesThis enables AI agents to query token balances, inspect NFT metadata, simulate transactions, and execute DeFi operations through natural language.
Documentation: https://docs.ucai.tech
GitHub: https://github.com/nirholas/UCAI
PyPI: https://pypi.org/project/abi-to-mcp/
Web App: https://mcp.ucai.tech
How Has This Been Tested?
Breaking Changes
None - this is a new addition to the registry.Types of changes
Checklist
Additional context
UCAI follows the Model Context Protocol specification and generates servers using the official MCP Python SDK. All generated servers include:
Description
Publishing Your Server
Note: We are no longer accepting PRs to add servers to the README. Instead, please publish your server to the MCP Server Registry to make it discoverable to the MCP ecosystem.
To publish your server, follow the quickstart guide. You can browse published servers at https://registry.modelcontextprotocol.io/.
Server Details
Motivation and Context
How Has This Been Tested?
Breaking Changes
Types of changes
Checklist
Additional context